Build Monitoring Synchronization

This synchronization method monitors a user’s build command and recognizes compiler processes that are spawned, extracts files and settings from a user’s project and adds them to the Helix QAC project. The process is usually fully automatic and can be repeated whenever a user project changes. However, it relies on performing a build of the user’s software which sometimes can be a lengthy procedure.

There are two types of Build Monitoring methods available:

  • Process Injection - This is the newest synchronization method and the preferred option. Select Process Injection from the Sync type drop-down in the synchronization dialog.
  • Process Monitor - This is the older, original method of synchronization. It works in a similar way to Process Injection but may be used if you run into issues with Process Injection. Select Process Monitor from the Sync type drop-down in the synchronization dialog.

To use the build monitoring synchronization methods with QA·GUI, it is necessary to use a script. To do this, it is necessary to either specify the working directory explicitly using the Optional Working Directory field, or to use the script specified in the Enter Build Command field to modify the directory in which you want to build your project.

A full build must be performed when doing a synchronization. Any existing files in the Helix QAC project will be removed if they are not in the current build.
For the synchronization methods that involve providing a build command, using a space in the path or project name can cause problems. If spaces are required, the build command should be placed in a script file to avoid parsing problems with the shell.